Fix Heroku build failure: add NODE_OPTIONS to build script for Node 18 compatibility#424
Merged
Conversation
webpack 4 (bundled with react-scripts 4) uses legacy OpenSSL digest algorithms not supported in Node 18. The start script already had this flag; the build script was missing it, causing ERR_OSSL_EVP_UNSUPPORTED on Heroku.
Member
|
[diff-counting] Significant lines: 0. |
laurenp-2
approved these changes
Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
webpack 4 (bundled with react-scripts 4) uses legacy OpenSSL digest algorithms unsupported in Node 18. The start
script already had this flag, but the build script was missing it, causing ERR_OSSL_EVP_UNSUPPORTED on Heroku.
Test Plan
Heroku staging build succeeded after setting NODE_OPTIONS=--openssl-legacy-provider as a config var (equivalent
workaround). This PR makes the fix permanent in code so the config var is no longer needed.
Notes
The Heroku config var NODE_OPTIONS=--openssl-legacy-provider can be removed after this merges — it will be
redundant. This is a short-term fix; long-term solution is upgrading to react-scripts 5 or Vite (tracked in TODO).